Summary

Count concurrent query outcomes only when the query completes within the configured benchmark window.

Why

Workers currently check the deadline before starting a query, but increment their counters after it finishes regardless of completion time. A query started just before the deadline can finish much later and still be included in concurrent_qps, which is divided by the original fixed duration.

With two workers, a two-second window, and queries that take three seconds, no query completes during the window, but the current code reports 1.000 QPS. After this change both late completions are excluded and the result is null. Workers still finish their in-flight queries normally; this does not introduce client cancellation or leave server-side work behind.

Testing

• real bench_concurrent_qps probe: late successes produce null QPS
• real bench_concurrent_qps probe: late failures produce null error ratio
• real bench_concurrent_qps probe: in-window successes are still counted
• bash -n lib/benchmark-common.sh
• shellcheck lib/benchmark-common.sh
• git diff --check